App requirements — the master entry point
The App requirements set (SPEC-APP) carries one requirement document per app, each inheriting the platform. This is its master page: the index of the six app documents and the rules every one of them follows.
1The six app documents
Six web apps share one shell and one session; each carries a canonical badge identity (hue, icon, label) defined in DS v2. Every app has exactly one requirement document, listed here in navigation order.
| App | Domain | Audience | Id | Status |
|---|---|---|---|---|
| Account — organization & identity management per tenant | account.riversync.com | Customer & partner orgs | SPEC-APP-ACC | v0.7 · actively prototyped |
| Portal — customer device monitoring | portal.riversync.com | Customer orgs | SPEC-APP-PTL | v0.5 · draft |
| Partners — partner service workspace | partner.riversync.com | Partner orgs | SPEC-APP-PAR | v0.3 · draft |
| Pipeline — RiverSync sales pipeline | pipeline.riversync.com | RiverSync users | SPEC-APP-PIP | v0.3 · draft |
| Admin — RiverSync platform console | admin.riversync.com | RiverSync users | SPEC-APP-ADM | v0.2 · draft |
| Field — RiverSync on-site service (mobile/tablet) | field.riversync.com | RiverSync users (engineers) | SPEC-APP-FLD | v0.2 · prototyped |
2What an app document owns
An app document specifies the app-scoped requirements only — its screens, navigation, menu visibility, surfaces and behaviours. Platform-wide concerns (tenancy, identity, authorization, partner agreements, products, data lifecycle) stay in the platform master and are referenced, never restated.
Each app carries its own requirement-line prefix (§3) so a requirement is traceable to exactly one app. Cross-cutting Federation requirements (FED-) are shared by every membership-gated app and live in the Federation PRD.
Every app document is a derivation target: its requirements flow into the data model (SPEC-ERD), Domain-Driven Design (SPEC-DDD), data workflows (SPEC-DWF) and process workflows (SPEC-PWF). A new screen, field or entity in a prototype must map to an app requirement or the master — if none exists, add it in the same turn.